abkhaz: ⟨ҩ⟩ is pharyngealized, and an identical glide twin is not its own vowel context - #768

…t (and refresh ab)

`tools/language-catalogue/derive-normalization.py` decides the `normalization` column from exactly
two things — does the engine directory have a `normalize.ts`, and does the engine call it. pcm's
treatment (#781) put its pre-tokenizer rewrites INLINE in naija.ts, so the column stayed empty and
pcm read as UNTREATED in the planning query the catalogue exists to serve. Typing `done` into the
TSV would have been overwritten on the next run.

⚠ Of the 62 engine DIRECTORIES that use the symbol tier (73 registry codes, several sharing a
directory), naija was the ONLY one with no normalize.ts — checked, not assumed. So this is pcm
being unconventional, not the tool being narrow, and the fix is to be conventional rather than to
teach the tool a second pattern it would then have to keep matching.

Moves the abbreviation expansion (a text rewrite, the same slot Hausa's `normalizeHausa` occupies)
into src/languages/naija/normalize.ts. The SYMBOL tier stays in naija.ts with the engine data, as it
does for ha/af/ur. No behaviour change: 3192 tests unchanged, and the call site is still
SYMBOLS(normalizeNaija(input)) — the order was deliberate.

⚠ THE .db REBUILD IS NOT A TWO-CELL CHANGE. main's committed languages.db did not match main's own
catalogue.tsv: a fresh build differs on 60 rows, staleness accumulated because the TSV has been
edited (e.g. #768/#769 rewrote ab's notes) without rebuilding the binary. This commit's .db is
byte-identical to a fresh build, so it also flushes those 59 unrelated rows — which is why the
binary diff is large for a change described as two cells.

Regenerating the column also picked up a second stale cell unrelated to this work: `ab` (Abkhaz)
has had a normalize.ts since its own treatment landed and was still reported as untreated. Both are
now `done` — 82 → 83, (none) 113 → 112.

The `pr` column is left empty, matching ha and ab: it carries a value in only 7 of 212 rows and
three of those hold stray note text, so it is not a maintained convention to opt into here.

⚠ The derivation and the .db build are both hand-run, which is how ab and the 60 rows drifted. A
`--check` gate in `npm run ci` (the shape check:package already uses) would catch both classes;
flagged rather than done here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J9yuDGsezBBo5myS3AeN7D

…t (and refresh ab) (#782)

`tools/language-catalogue/derive-normalization.py` decides the `normalization` column from exactly
two things — does the engine directory have a `normalize.ts`, and does the engine call it. pcm's
treatment (#781) put its pre-tokenizer rewrites INLINE in naija.ts, so the column stayed empty and
pcm read as UNTREATED in the planning query the catalogue exists to serve. Typing `done` into the
TSV would have been overwritten on the next run.

⚠ Of the 62 engine DIRECTORIES that use the symbol tier (73 registry codes, several sharing a
directory), naija was the ONLY one with no normalize.ts — checked, not assumed. So this is pcm
being unconventional, not the tool being narrow, and the fix is to be conventional rather than to
teach the tool a second pattern it would then have to keep matching.

Moves the abbreviation expansion (a text rewrite, the same slot Hausa's `normalizeHausa` occupies)
into src/languages/naija/normalize.ts. The SYMBOL tier stays in naija.ts with the engine data, as it
does for ha/af/ur. No behaviour change: 3192 tests unchanged, and the call site is still
SYMBOLS(normalizeNaija(input)) — the order was deliberate.

⚠ THE .db REBUILD IS NOT A TWO-CELL CHANGE. main's committed languages.db did not match main's own
catalogue.tsv: a fresh build differs on 60 rows, staleness accumulated because the TSV has been
edited (e.g. #768/#769 rewrote ab's notes) without rebuilding the binary. This commit's .db is
byte-identical to a fresh build, so it also flushes those 59 unrelated rows — which is why the
binary diff is large for a change described as two cells.

Regenerating the column also picked up a second stale cell unrelated to this work: `ab` (Abkhaz)
has had a normalize.ts since its own treatment landed and was still reported as untreated. Both are
now `done` — 82 → 83, (none) 113 → 112.

The `pr` column is left empty, matching ha and ab: it carries a value in only 7 of 212 rows and
three of those hold stray note text, so it is not a maintained convention to opt into here.

⚠ The derivation and the .db build are both hand-run, which is how ab and the 60 rows drifted. A
`--check` gate in `npm run ci` (the shape check:package already uses) would catch both classes;
flagged rather than done here.


Claude-Session: https://claude.ai/code/session_01J9yuDGsezBBo5myS3AeN7D

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>